feat(RELEASE-2314): multiarch verification for push-to-external-registry-idempotent by midnightercz · Pull Request #2330 · konflux-ci/release-service-catalog

midnightercz · 2026-06-26T13:48:07Z

Added support to verify multiarch images for push-to-external-registry-idempotent

Describe your changes

Relevant Jira

Checklist before requesting a review

I have marked as draft or added do not merge label if there's a dependency PR
- If you want reviews on your draft PR, you can add reviewers or add the release-service-maintainers handle if you are unsure who to tag
My commit message includes Signed-off-by: My name <email>
I read CONTRIBUTING.MD and commit formatting
I have run the README.md generator script in .github/scripts/readme_generator.sh and verified the results using .github/scripts/check_readme.sh
If an AI agent was used, I marked that via a commit footer like Assisted-By: Cursor

Copilot

Pull request overview

Adds multi-architecture image verification to the push-to-external-registry-idempotent integration test flow so the suite can validate that published release artifacts include the expected set of architectures (instead of only checking a single arch).

Changes:

Introduces a PTSV_EXPECTED_ARCHES variable intended to drive multi-arch verification behavior.
Updates the push-to-external-registry-idempotent test to compare the release’s arches list against the expected arches when provided.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
integration-tests/run-test.sh	Initializes `PTSV_EXPECTED_ARCHES` for the integration test runner environment.
integration-tests/push-to-external-registry-idempotent/test.sh	Adds conditional multi-arch verification logic based on `PTSV_EXPECTED_ARCHES`.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

midnightercz · 2026-06-29T09:45:03Z

/retest

qodo-app-for-konflux-ci · 2026-06-30T11:43:47Z

PR Reviewer Guide 🔍

(Review updated until commit `bd80323`)

Warning

/review is deprecated. Use /agentic_review instead (removal date not yet scheduled).

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪
🧪 No relevant tests
🔒 No security concerns identified
⚡ Recommended focus areas for review Order Sensitivity The multi-arch validation compares a space-joined, sorted list of arches from the release JSON to an expected string. This is order/format sensitive and can fail if the expected value isn’t normalized the same way (sorting, spacing). Consider normalizing `PTSV_EXPECTED_ARCHES` similarly (e.g., split/sort/join) or comparing sets instead of raw strings. if [ -n "${PTSV_EXPECTED_ARCHES:-}" ]; then local image_arches image_arches=$(jq -r '.status.artifacts.images[0]?.arches // [] \| sort \| join(" ")' <<< "${release_json}") if [ "${image_arches}" = "${PTSV_EXPECTED_ARCHES}" ]; then echo "✅️ Found required image arches: $PTSV_EXPECTED_ARCHES" else echo "🔴 Expected image arches: '$PTSV_EXPECTED_ARCHES', found: ${image_arches}" failures=$((failures+1)) fi Bash Robustness The new jq pipeline defaults to an empty array, but `join(" ")` produces an empty string; if the release has no arches, the error message prints an empty “found” value. Consider making the failure output more explicit (e.g., printing “”) and ensuring the jq expression always yields predictable output. Also consider quoting variable expansions consistently in echo/error paths. local image_arches image_arches=$(jq -r '.status.artifacts.images[0]?.arches // [] \| sort \| join(" ")' <<< "${release_json}") if [ "${image_arches}" = "${PTSV_EXPECTED_ARCHES}" ]; then echo "✅️ Found required image arches: $PTSV_EXPECTED_ARCHES" else echo "🔴 Expected image arches: '$PTSV_EXPECTED_ARCHES', found: ${image_arches}" failures=$((failures+1)) fi else image_arch=$(jq -r '.status.artifacts.images[0]?.arches[0] // ""' <<< "${release_json}") echo "Checking Image Arch..." if [ -n "${image_arch}" ]; then echo "✅️ image_arch: ${image_arch}" else echo "🔴 image_arch was empty" failures=$((failures+1)) fi Simplify Init The added empty-default initialization for `PTSV_EXPECTED_ARCHES` can be simplified and made safer/clearer using parameter expansion (e.g., `: "${PTSV_EXPECTED_ARCHES:=}"`) and consistent quoting. Also consider whether this variable should be exported here if it’s relied on in sub-scripts. if [ -z "$PTSV_EXPECTED_ARCHES" ]; then PTSV_EXPECTED_ARCHES="" fi

qodo-app-for-konflux-ci · 2026-06-30T11:47:36Z

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

Context used

✅ Compliance rules (platform): 28 rules

1. ~~Missing then in if~~ ✓ Resolved 🐞 Bug ≡ Correctness

Description

verify_single_release() introduces an if statement without a required then, making
integration-tests/push-to-external-registry-idempotent/test.sh a bash syntax error and causing the
suite to fail when sourced/executed.

Code

integration-tests/push-to-external-registry-idempotent/test.sh[R50-52]

+    if [ -s "$PTSV_EXPECTED_ARCHES" ]
+      image_arches=$(jq -r '.status.artifacts.images[0]?.arches // [] | sort | join(" ")' <<< "${release_json}")
+      if [ "${image_arches}" = "$PTSV_EXPECTED_ARCHES" ]; then

Relevance

⭐⭐⭐ High
Team consistently fixes bash-breaking issues; run-test.sh sources suite scripts so syntax error
would stop CI.
PR-#2181

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The suite script contains an if line with no following then, and the main runner sources this
file, so bash will fail to parse the script and the test cannot run.
integration-tests/push-to-external-registry-idempotent/test.sh[49-60]
integration-tests/run-test.sh[142-148]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`integration-tests/push-to-external-registry-idempotent/test.sh` contains an `if [ ... ]` without `then`, which is a bash parse error.

### Issue Context
This test suite is sourced by `integration-tests/run-test.sh`, so a parse error in the suite script will break the whole integration test run.

### Fix Focus Areas
- integration-tests/push-to-external-registry-idempotent/test.sh[50-58]
- integration-tests/run-test.sh[142-148]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

2. PTSV_EXPECTED_ARCHES missing braces ✓ Resolved 📘 Rule violation ⚙ Maintainability

Description

The updated multi-arch shell logic expands PTSV_EXPECTED_ARCHES using bare $PTSV_EXPECTED_ARCHES
instead of the required brace form ${PTSV_EXPECTED_ARCHES}. This violates the shell variable
expansion requirement and can cause ambiguous parsing/expansion when the variable is adjacent to
other characters.

Code

integration-tests/push-to-external-registry-idempotent/test.sh[R50-56]

+    if [ -s "$PTSV_EXPECTED_ARCHES" ]
+      image_arches=$(jq -r '.status.artifacts.images[0]?.arches // [] | sort | join(" ")' <<< "${release_json}")
+      if [ "${image_arches}" = "$PTSV_EXPECTED_ARCHES" ]; then
+          echo "✅️ Found required image arches: $PTSV_EXPECTED_ARCHES"
+      else
+          echo "🔴 Expected image arches: '$PTSV_EXPECTED_ARCHES', found: ${image_arches}"
+          failures=$((failures+1))

Relevance

⭐⭐ Medium
No historical reviews enforcing ${VAR} over $VAR in integration-tests; team often focuses on
functional issues.
ⓘ Recommendations generated based on similar findings in past PRs

Evidence

PR Compliance ID 1264 requires brace syntax for expansion of non-special shell variables. In the
newly added/modified multi-arch verification and guard/initialization logic, PTSV_EXPECTED_ARCHES
is referenced as $PTSV_EXPECTED_ARCHES (including in an if test condition and in related
statements such as echo/output), which directly demonstrates non-compliance with the rule that
mandates ${PTSV_EXPECTED_ARCHES}.

Rule 1264: Use brace syntax for shell variable expansion
integration-tests/push-to-external-registry-idempotent/test.sh[50-56]
integration-tests/run-test.sh[172-174]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`PTSV_EXPECTED_ARCHES` is currently expanded using bare `$PTSV_EXPECTED_ARCHES` in newly added/modified multi-arch logic, but PR Compliance ID 1264 requires brace syntax (`${VAR}`) for non-special shell variables. Update these references to use `${PTSV_EXPECTED_ARCHES}` to satisfy the compliance rule and avoid ambiguous expansions when concatenated with adjacent characters.

## Issue Context
This was introduced as part of the new multi-arch verification support, including a guard clause / initialization logic and the modified verification block.

## Fix Focus Areas
- integration-tests/push-to-external-registry-idempotent/test.sh[50-56]
- integration-tests/run-test.sh[172-174]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

3. ~~Wrong -s variable check~~ ✓ Resolved 🐞 Bug ≡ Correctness

Description

verify_single_release() uses [ -s "$PTSV_EXPECTED_ARCHES" ], which checks for a non-empty file,
but PTSV_EXPECTED_ARCHES is set/used as a string of expected arches; this breaks the intended
branch selection for multiarch verification.

Code

integration-tests/push-to-external-registry-idempotent/test.sh[R50-56]

+    if [ -s "$PTSV_EXPECTED_ARCHES" ]
+      image_arches=$(jq -r '.status.artifacts.images[0]?.arches // [] | sort | join(" ")' <<< "${release_json}")
+      if [ "${image_arches}" = "$PTSV_EXPECTED_ARCHES" ]; then
+          echo "✅️ Found required image arches: $PTSV_EXPECTED_ARCHES"
+      else
+          echo "🔴 Expected image arches: '$PTSV_EXPECTED_ARCHES', found: ${image_arches}"
+          failures=$((failures+1))

Relevance

⭐⭐⭐ High
PTSV_EXPECTED_ARCHES treated as string elsewhere; using -s (file test) likely breaks multiarch
branch, so will fix.
PR-#2181
PR-#2252

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
run-test.sh treats PTSV_EXPECTED_ARCHES as a plain env var string (defaulting to ""), while
test.sh uses -s which is a file test and therefore does not reflect whether the string is set.
integration-tests/push-to-external-registry-idempotent/test.sh[50-67]
integration-tests/run-test.sh[150-175]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The code uses `-s` (file-size test) on `PTSV_EXPECTED_ARCHES`, but the variable is an environment string (e.g., `"amd64 arm64"`). This makes the condition incorrect and can cause the multiarch comparison branch to be skipped.

### Issue Context
`run-test.sh` initializes `PTSV_EXPECTED_ARCHES` as an empty string when not provided and otherwise populates it from `PIPELINE_TEST_SUITE_VARS` exports, indicating it is a string variable, not a path.

### Fix Focus Areas
- integration-tests/push-to-external-registry-idempotent/test.sh[50-67]
- integration-tests/run-test.sh[156-175]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

4. Arches compare order-sensitive 🐞 Bug ≡ Correctness ⭐ New

Description

verify_single_release() sorts the arches extracted from the Release JSON but compares them to
PTSV_EXPECTED_ARCHES without normalizing/sorting the expected list, so the same set of arches in a
different order (or with extra whitespace) will fail the test. This can cause flaky/incorrect
integration test failures when PTSV_EXPECTED_ARCHES is provided externally (e.g., via
PIPELINE_TEST_SUITE_VARS).

Code

integration-tests/push-to-external-registry-idempotent/test.sh[R50-58]

+    if [ -n "${PTSV_EXPECTED_ARCHES:-}" ]; then
+        local image_arches
+        image_arches=$(jq -r '.status.artifacts.images[0]?.arches // [] | sort | join(" ")' <<< "${release_json}")
+        if [ "${image_arches}" = "${PTSV_EXPECTED_ARCHES}" ]; then
+          echo "✅️ Found required image arches: $PTSV_EXPECTED_ARCHES"
+      else
+          echo "🔴 Expected image arches: '$PTSV_EXPECTED_ARCHES', found: ${image_arches}"
+          failures=$((failures+1))
+      fi

Relevance

⭐ Low
Repo already uses sorted-actual vs exact-string arches equality; vars imported verbatim; no prior
normalization enforcement seen.
PR-#2252
PR-#2181

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The test sorts the actual arches list from the Release JSON but directly compares against the raw
expected string, while run-test.sh imports PTSV_* values verbatim from JSON without any
normalization; another suite demonstrates the canonical sorted format for arches checks.
integration-tests/push-to-external-registry-idempotent/test.sh[50-58]
integration-tests/run-test.sh[156-163]
integration-tests/rh-push-to-external-registry/test.sh[33-53]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`verify_single_release()` canonicalizes the *actual* arches (`sort | join(" ")`) but compares against `PTSV_EXPECTED_ARCHES` verbatim. This makes the test incorrectly fail if `PTSV_EXPECTED_ARCHES` has the same arches but in a different order or with inconsistent whitespace.

## Issue Context
`PTSV_EXPECTED_ARCHES` is intended to be set externally (commonly through `PIPELINE_TEST_SUITE_VARS`), so it should be treated as untrusted/un-normalized input.

## Fix Focus Areas
- Normalize `PTSV_EXPECTED_ARCHES` to the same canonical representation as `image_arches` (split on whitespace, sort, re-join with single spaces; also trim).
- Optionally support JSON-array form too (e.g., if a user supplies `["amd64","arm64"]`), by detecting leading `[` and using `jq -r 'fromjson|sort|join(" ")'`.

### Suggested code approach (bash)
- Compute `expected_arches_normalized` and compare `image_arches` to that.

## Fix Focus Areas (code locations)
- integration-tests/push-to-external-registry-idempotent/test.sh[50-58]
- integration-tests/run-test.sh[156-163]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Previous review results

Review updated until commit bd80323

Results up to commit e232caf

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0) 🎨 UX issues (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

1. ~~Missing then in if~~ ✓ Resolved 🐞 Bug ≡ Correctness

Description

verify_single_release() introduces an if statement without a required then, making
integration-tests/push-to-external-registry-idempotent/test.sh a bash syntax error and causing the
suite to fail when sourced/executed.

Code

integration-tests/push-to-external-registry-idempotent/test.sh[R50-52]

+    if [ -s "$PTSV_EXPECTED_ARCHES" ]
+      image_arches=$(jq -r '.status.artifacts.images[0]?.arches // [] | sort | join(" ")' <<< "${release_json}")
+      if [ "${image_arches}" = "$PTSV_EXPECTED_ARCHES" ]; then

Relevance

⭐⭐⭐ High
Team consistently fixes bash-breaking issues; run-test.sh sources suite scripts so syntax error
would stop CI.
PR-#2181

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The suite script contains an if line with no following then, and the main runner sources this
file, so bash will fail to parse the script and the test cannot run.
integration-tests/push-to-external-registry-idempotent/test.sh[49-60]
integration-tests/run-test.sh[142-148]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`integration-tests/push-to-external-registry-idempotent/test.sh` contains an `if [ ... ]` without `then`, which is a bash parse error.

### Issue Context
This test suite is sourced by `integration-tests/run-test.sh`, so a parse error in the suite script will break the whole integration test run.

### Fix Focus Areas
- integration-tests/push-to-external-registry-idempotent/test.sh[50-58]
- integration-tests/run-test.sh[142-148]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

2. PTSV_EXPECTED_ARCHES missing braces ✓ Resolved 📘 Rule violation ⚙ Maintainability

Description

The updated multi-arch shell logic expands PTSV_EXPECTED_ARCHES using bare $PTSV_EXPECTED_ARCHES
instead of the required brace form ${PTSV_EXPECTED_ARCHES}. This violates the shell variable
expansion requirement and can cause ambiguous parsing/expansion when the variable is adjacent to
other characters.

Code

integration-tests/push-to-external-registry-idempotent/test.sh[R50-56]

+    if [ -s "$PTSV_EXPECTED_ARCHES" ]
+      image_arches=$(jq -r '.status.artifacts.images[0]?.arches // [] | sort | join(" ")' <<< "${release_json}")
+      if [ "${image_arches}" = "$PTSV_EXPECTED_ARCHES" ]; then
+          echo "✅️ Found required image arches: $PTSV_EXPECTED_ARCHES"
+      else
+          echo "🔴 Expected image arches: '$PTSV_EXPECTED_ARCHES', found: ${image_arches}"
+          failures=$((failures+1))

Relevance

⭐⭐ Medium
No historical reviews enforcing ${VAR} over $VAR in integration-tests; team often focuses on
functional issues.
ⓘ Recommendations generated based on similar findings in past PRs

Evidence

PR Compliance ID 1264 requires brace syntax for expansion of non-special shell variables. In the
newly added/modified multi-arch verification and guard/initialization logic, PTSV_EXPECTED_ARCHES
is referenced as $PTSV_EXPECTED_ARCHES (including in an if test condition and in related
statements such as echo/output), which directly demonstrates non-compliance with the rule that
mandates ${PTSV_EXPECTED_ARCHES}.

Rule 1264: Use brace syntax for shell variable expansion
integration-tests/push-to-external-registry-idempotent/test.sh[50-56]
integration-tests/run-test.sh[172-174]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`PTSV_EXPECTED_ARCHES` is currently expanded using bare `$PTSV_EXPECTED_ARCHES` in newly added/modified multi-arch logic, but PR Compliance ID 1264 requires brace syntax (`${VAR}`) for non-special shell variables. Update these references to use `${PTSV_EXPECTED_ARCHES}` to satisfy the compliance rule and avoid ambiguous expansions when concatenated with adjacent characters.

## Issue Context
This was introduced as part of the new multi-arch verification support, including a guard clause / initialization logic and the modified verification block.

## Fix Focus Areas
- integration-tests/push-to-external-registry-idempotent/test.sh[50-56]
- integration-tests/run-test.sh[172-174]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

3. ~~Wrong -s variable check~~ ✓ Resolved 🐞 Bug ≡ Correctness

Description

verify_single_release() uses [ -s "$PTSV_EXPECTED_ARCHES" ], which checks for a non-empty file,
but PTSV_EXPECTED_ARCHES is set/used as a string of expected arches; this breaks the intended
branch selection for multiarch verification.

Code

integration-tests/push-to-external-registry-idempotent/test.sh[R50-56]

+    if [ -s "$PTSV_EXPECTED_ARCHES" ]
+      image_arches=$(jq -r '.status.artifacts.images[0]?.arches // [] | sort | join(" ")' <<< "${release_json}")
+      if [ "${image_arches}" = "$PTSV_EXPECTED_ARCHES" ]; then
+          echo "✅️ Found required image arches: $PTSV_EXPECTED_ARCHES"
+      else
+          echo "🔴 Expected image arches: '$PTSV_EXPECTED_ARCHES', found: ${image_arches}"
+          failures=$((failures+1))

Relevance

⭐⭐⭐ High
PTSV_EXPECTED_ARCHES treated as string elsewhere; using -s (file test) likely breaks multiarch
branch, so will fix.
PR-#2181
PR-#2252

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
run-test.sh treats PTSV_EXPECTED_ARCHES as a plain env var string (defaulting to ""), while
test.sh uses -s which is a file test and therefore does not reflect whether the string is set.
integration-tests/push-to-external-registry-idempotent/test.sh[50-67]
integration-tests/run-test.sh[150-175]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The code uses `-s` (file-size test) on `PTSV_EXPECTED_ARCHES`, but the variable is an environment string (e.g., `"amd64 arm64"`). This makes the condition incorrect and can cause the multiarch comparison branch to be skipped.

### Issue Context
`run-test.sh` initializes `PTSV_EXPECTED_ARCHES` as an empty string when not provided and otherwise populates it from `PIPELINE_TEST_SUITE_VARS` exports, indicating it is a string variable, not a path.

### Fix Focus Areas
- integration-tests/push-to-external-registry-idempotent/test.sh[50-67]
- integration-tests/run-test.sh[156-175]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

qodo-app-for-konflux-ci · 2026-07-01T07:01:09Z

Code Review by Qodo

Sorry, something went wrong

We weren't able to complete the code review on our side. Please try again

qodo-app-for-konflux-ci · 2026-07-01T08:33:08Z

Code Review by Qodo

Sorry, something went wrong

We weren't able to complete the code review on our side. Please try again

happybhati

LGTM, holding approvel until e2e pass!

midnightercz · 2026-07-02T07:20:09Z

/retest

midnightercz · 2026-07-03T07:13:47Z

/retest

Added support to verify multiarch images for push-to-external-registry-idempotent Signed-off-by: Jindrich Luza <jluza@redhat.com>

qodo-app-for-konflux-ci · 2026-07-03T11:57:10Z

Code review by qodo was updated up to the latest commit bd80323

release-service-bot assigned FilipNikolovski and happybhati Jun 26, 2026

midnightercz force-pushed the RELEASE-2314-multiarch-verification branch 2 times, most recently from ae52b7a to 32539ec Compare June 29, 2026 08:17

Copilot AI review requested due to automatic review settings June 29, 2026 08:17

Copilot started reviewing on behalf of midnightercz June 29, 2026 08:18 View session

midnightercz force-pushed the RELEASE-2314-multiarch-verification branch from 32539ec to 92758e7 Compare June 29, 2026 08:19

Copilot AI reviewed Jun 29, 2026

View reviewed changes

Comment thread integration-tests/push-to-external-registry-idempotent/test.sh Outdated

midnightercz force-pushed the RELEASE-2314-multiarch-verification branch from 92758e7 to 73b90d5 Compare June 29, 2026 08:27

midnightercz force-pushed the RELEASE-2314-multiarch-verification branch from 73b90d5 to e232caf Compare June 30, 2026 11:42

qodo-app-for-konflux-ci Bot added the Review effort 2/5 label Jun 30, 2026

qodo-app-for-konflux-ci Bot reviewed Jun 30, 2026

View reviewed changes

Comment thread integration-tests/push-to-external-registry-idempotent/test.sh Outdated

Comment thread integration-tests/push-to-external-registry-idempotent/test.sh Outdated

midnightercz force-pushed the RELEASE-2314-multiarch-verification branch 2 times, most recently from 34c2ee5 to 1d85481 Compare July 1, 2026 06:54

midnightercz force-pushed the RELEASE-2314-multiarch-verification branch from 1d85481 to 7313558 Compare July 1, 2026 08:18

happybhati reviewed Jul 2, 2026

View reviewed changes

feat(RELEASE-2314): ma test for push-to-external-registry-idempotent

bd80323

Added support to verify multiarch images for push-to-external-registry-idempotent Signed-off-by: Jindrich Luza <jluza@redhat.com>

midnightercz force-pushed the RELEASE-2314-multiarch-verification branch from 7313558 to bd80323 Compare July 3, 2026 11:51

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat(RELEASE-2314): multiarch verification for push-to-external-registry-idempotent#2330

feat(RELEASE-2314): multiarch verification for push-to-external-registry-idempotent#2330
midnightercz wants to merge 1 commit into
developmentfrom
RELEASE-2314-multiarch-verification

midnightercz commented Jun 26, 2026

Uh oh!

Copilot AI left a comment

Uh oh!

Uh oh!

midnightercz commented Jun 29, 2026

Uh oh!

qodo-app-for-konflux-ci Bot commented Jun 30, 2026 •

edited

Loading

Uh oh!

qodo-app-for-konflux-ci Bot commented Jun 30, 2026 •

edited

Loading

Uh oh!

Uh oh!

Uh oh!

qodo-app-for-konflux-ci Bot commented Jul 1, 2026

Uh oh!

qodo-app-for-konflux-ci Bot commented Jul 1, 2026

Uh oh!

happybhati left a comment

Uh oh!

midnightercz commented Jul 2, 2026

Uh oh!

midnightercz commented Jul 3, 2026

Uh oh!

qodo-app-for-konflux-ci Bot commented Jul 3, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Uh oh!

Conversation

midnightercz commented Jun 26, 2026

Describe your changes

Relevant Jira

Checklist before requesting a review

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

midnightercz commented Jun 29, 2026

Uh oh!

qodo-app-for-konflux-ci Bot commented Jun 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR Reviewer Guide 🔍

(Review updated until commit bd80323)

Uh oh!

qodo-app-for-konflux-ci Bot commented Jun 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Code Review by Qodo

Previous review results

Uh oh!

Uh oh!

Uh oh!

qodo-app-for-konflux-ci Bot commented Jul 1, 2026

Code Review by Qodo

Sorry, something went wrong

Uh oh!

qodo-app-for-konflux-ci Bot commented Jul 1, 2026

Code Review by Qodo

Sorry, something went wrong

Uh oh!

happybhati left a comment

Choose a reason for hiding this comment

Uh oh!

midnightercz commented Jul 2, 2026

Uh oh!

midnightercz commented Jul 3, 2026

Uh oh!

qodo-app-for-konflux-ci Bot commented Jul 3, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

qodo-app-for-konflux-ci Bot commented Jun 30, 2026 •

edited

Loading

(Review updated until commit `bd80323`)

qodo-app-for-konflux-ci Bot commented Jun 30, 2026 •

edited

Loading